home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr31
/
udproc12.zip
/
UDPROC.DOC
< prev
next >
Wrap
Text File
|
1993-05-01
|
20KB
|
471 lines
UDPROC
Upload Directory PROCessor
Version 1.02
Copyright 1990
by
ZebbWare Products
39 Wilson Road
Portsmouth, NH 03801-5737
(603)433-5969
BBS: (603)436-7475 (300-9600+ baud)
ALL RIGHTS RESERVED!
******************** (TM)
********************
...... ***....
.. *** ..
.. ..*** ..
.. .... ..
.. *** .. ..
.*** .... *
***. .. **
*******************
********************
Table of Contents
What Am I?.................................................1
Introduction...............................................1
License, Prices, Warnings & Copyrights.................1
Contacting ZebbWare Products...........................2
Other 'ZebbWare Products' Products.....................2
List of Files on Disk (or in Archive)..................2
Using the Upload Directory PROCessor.......................3
Option /D (Directory to process)......................3
Option /H (Header file to use)........................4
Option /O# (Override automatic deletion)..............4
Option /W (Write over existing archives)..............5
Option /T (Time & Date Stamping)......................5
Option /F (FILES.BBS processing)......................5
Option /A (Add Missing files to FILES.BBS)............5
Example (program flow).....................................6
Temporary Files & Directory................................7
Error & Return Codes.......................................7
Required Programs (Setup & Memory Information!)............7
Last Word..................................................7
Upload Directory Processor (C) 1990 ZebbWare Products 16/Jan/1990 Page 1
What Am I?
The Upload Directory PROCessor (UDPROC.EXE) will test & convert
all archives in a given directory to the PAK format. Optionally
saving the original & the damaged archives. It will update a
FILES.BBS file to reflect the new file extension. It will use the
original archives date & time stamp for the new PAK file.
Introduction
The Upload Directory Processor was originally designed for my use
with an Opus-Based Bulletin Board System. However, it can & does
work on any directory without an Opus BBS installed. I needed a
utility that would perform various tasks on each archive file in a
given directory. Those various tasks were: 1) Test the archives for
any damage (CRC errors, etc...). 2) If they were damaged, then either
delete them or rename them to *.DAM. 3a) If they were intact and
they were in the 'PAK' format, I would run the PAK program with the
C option (PAK C FILENAME) to be sure the file was PAK'd with the newest
version of PAK (currently v2.10). 3b) If they were in the ZIP or
LZH format, I would convert them to 'PAK' format. (If they were ARC
format I would rename it to PAK and process accordingly). 4) I would
add an extended header to the newly tested/converted PAK file (PAK H).
5) I would then change the date & time of the new archive to match
the old archives date & time. This was so my BBS users would not think
these files were new uploads if they had already seen them under the
old archive format. 6) I would update the FILES.BBS file (for opus) to
reflect the new file extension. This is what this program basically does!
It does, however, have a few options. (explained further below)
License, Prices, Warnings & Copyrights
The Upload Directory Processor is a copyrighted work, protected
by United States law and international treaty provisions. There is
no charge for this program, however there is a $10 charge if you want
a copy of the source code. If you would like the C source code for
UDPROC.EXE, send a check or money order for $11.50 (1.50 ship & hndl)
to ZebbWare Products, Attention: Source Request Dept., 39 Wilson Road,
Portsmouth, New Hampshire 03801-5737.
Since there is no charge for the program, Please feel free to
distribute it to other bulletin boards & friends. Also, why not drop
me a card and let me know your thoughts!
THIS IS A USE AT YOUR OWN RISK PROGRAM!!! ZebbWare Products & the
the author will NOT be responsible for lost or damaged files. I make
no Guarantees or promises! It does, however, work fine for me!
UDPROC interfaces with the following OUTSTANDING compression programs:
PAK - (C) 1989, 1990 NoGate Consulting. All Rights Reserved.
PKZIP/PKUNZIP - (C) 1989 PKWARE Inc. All Rights Reserved.
LHARC - (C) 1989 Haruyasu Yoshizaki. All Rights Reserved.
Upload Directory Processor (C) 1990 ZebbWare Products 16/Jan/1990 Page 2
Contacting ZebbWare Products
If you wish to contact ZebbWare Products with questions,
comments, or suggestions, we can be reached several different ways.
You can call our answering machine at (603)433-5969.
or
You can call Spectre BBS at (603)436-7475 / 300-9600 HST /8N1,
FidoNet Address (1:132/202).
You can also address letters to:
ZebbWare Products
39 Wilson Road
Portsmouth, New Hampshire
03801-5737
Other 'ZebbWare Products' Products
SID, Software Inventory Database. A Nice way to keep track of
all your software. Database is stored in dBase III Plus file format
so dBase compatible products will be able to access the data.
Features include: Sorting, Variety of sorted reporting, Wastebasket
(all deleted entries are stored in the wastebasket until you empty it),
Add, Modify, Inquiry, Browse and more.
FLOPINS, a utility for creating inserts for floppy disks. No
longer will you have to squint to see what's written on a tiny
floppy label. Now you can create floppy inserts on your Epson
compatible printer. Slide these into your 5 1/4 floppy sleeve and
identifying whats on a floppy becomes a breeze.
ZebbWare Products also makes available custom programming in a wide
variety of languages for a wide variety of environments. Looking to
help the small / medium business get the most from computerization.
Please Write or Call for further information.
List of Files on Disk (or in Archive)
Your Upload Directory PROCessor disk should contain the
following files:
UDPROC.EXE - ZebbWare's Upload Directory PROCessor (18649 bytes)
UDPROC.DOC - This documentation you're reading right now!
README.1ST - (Optional) If this file exists, it will contain
any last minute information.
Upload Directory Processor (C) 1990 ZebbWare Products 16/Jan/1990 Page 3
Options
By typing UDPROC and hitting the ENTER key, UDPROC will display
a usage screen which looks something like this:
+---------------------------------------------------------------------+
| |
| ZebbWare Products (R) Upload Directory Processor Version 1.02 |
| Copyright (c)1990 ZebbWare Products - All Rights Reserved! |
| |
| usage: C:\DOS\UDPROC.EXE /D{path} [ switches... ] |
| Valid Switches are: |
| /d{path} or /D{path} - Path of directory to process |
| /h{path} or /H{path} - Path & Filename of extended header |
| /o# or /O# - Where # = 1, 2, or 3 |
| 1) Don't delete original archives |
| 2) Don't delete damaged archives (makes DAMAGED.BBS)|
| 3) Don't delete originals or damaged archives |
| /f or /F - Don't touch the FILES.BBS file |
| /t or /T - Don't keep original archive Creation date & time |
| /w or /W - Write over existing archives |
| |
| Example: C:\DOS\UDPROC.EXE /dc:\dos\workdir /Hc:header.txt /o2 |
| |
+---------------------------------------------------------------------+
The switches are as follows:
/d{path} or /D{path} where {path} is the FULL path of the
directory you want to convert.
For example, if you want to convert all archives in the
C:\OPUS\UPLOADS directory, you would execute the program like this:
UDPROC /DC:\OPUS\UPLOADS or UDPROC /dC:\opus\UpLoAdS
As you can see Upper & Lower case doesn't matter. If you
wanted to convert everything in the root directory of drive d: you
would use the program like this:
UDPROC /dd:\ or UDPROC /Dd:\
The /D switch is a REQUIRED switch. If you do not specify
this switch on the command line, you will be prompted to enter the
Directory you wish to process. (This is assuming you have entered at
least one other switch. If you don't specify the /D switch
and you don't specify any other switches, you will simply get the
usage screen shown above.)
If you enter an invalid path with the /D switch, UDPROC will
beep at you and tell you what directory couldn't be found. Try
entering garbage after the /d switch and you'll see what I mean.
Upload Directory Processor (C) 1990 ZebbWare Products 16/Jan/1990 Page 4
Options (continued)
/h{path} or /H{path} where {path} is the FULL path of the
file which represents the Extended Archive
header you wish to add to your archives.
For example, If you want to convert all archives in the C:\UPLOADS
directory and you wanted to include the header file D:\TEXT\HEADER.TXT,
you would execute the program like this:
UDPROC /dC:\UPLOADS /Hd:\text\header.txt
Again, Upper & lower case does not matter. If the
path/filename following the /H does not exist, UDPROC will beep at
you and tell you it couldn't find the file.
/o# or /O# Where # = 1, 2, or 3. - Overrides deletion of
archives. It will continue to rename *.ARC files
to *.PAK regardless of this switch.
/O1 - Overrides deletion of the original archives. (with
1 exception, see /W switch further on).
Example: If Drive C: root directory contains 2 files in it
(FILE1.ZIP & FILE2.LZH), when UDPROC is executed like this: UDPROC /Dc:\
/o1 it will convert FILE1.ZIP to FILE1.PAK and FILE2.LZH to FILE2.PAK.
With the /O1 switch specified, the directory will now contain 4 files:
FILE1.ZIP, FILE1.PAK, FILE2.LZH & FILE2.PAK. If this switch is NOT
used, the directory will only contain the *.PAK files.
/O2 - Overrides deletion of the damaged archives. Also
creates the DAMAGED.BBS file
If FILE1.ZIP turned out to contain errors in it (such as Bad CRC),
and the /O2 switch was specified, the damaged archive would be renamed
to FILE1.DAM. If the /O2 was not specified and FILE1.ZIP was damaged,
UDPROC will simply delete it.
OPUS: UDPROC will edit the FILES.BBS file (if found) to reflect
the new file extensions (assuming /f wasn't used). EVEN IF YOU USE
/O1 TO SAVE the original archives, FILES.BBS will still be updated.
The only exception is if you use the /O2 switch and the file is damaged.
UDPROC will then create a file called DAMAGED.BBS. It will extract the
filename & description of the damaged archive from the FILES.BBS file and
place it in the DAMAGED.BBS file.
/O3 - Is a combination of /O1 & /O2. It Overrides the
deletion of the Original archives as well as the
damaged archives. (See /O1 & /O2 for more info)
Upload Directory Processor (C) 1990 ZebbWare Products 16/Jan/1990 Page 5
Options (continued)
/w or /W write over existing .PAK archives
If the directory you're converting has 2 archives with the same
filename but different extensions, you have one of 2 options. Let's
assume the directory you're converting has 2 files in it called
FILE1.ZIP and FILE1.PAK. If you specifed the /W switch, UDPROC will
delete FILE1.PAK and then convert FILE1.ZIP into FILE1.PAK. If you
don't specify the /W switch, UDPROC will delete the FILE1.ZIP file
and test/convert FILE1.PAK.
UDPROC is not too kind here. You can keep one or the other but
not both. Perhaps if there is enough feedback, a future release will
allow you to keep both. If you really want this option, Contact
ZebbWare products and let us know!
/t or /T Time-Stamping override
UDPROC, by default, will keep the original archives date & time
stamp. If you're converting FILE1.ZIP and it was created 05-28-89 at
5:02am, then by default, FILE1.PAK will also show that it was created
05-28-89 at 5:02am.
If you specify the /T switch, then UDPROC will NOT keep the
original date & time stamp and FILE1.PAK will show that it was
created Today. (Uses PC's System clock)
/f or /F FILES.BBS file processing override
UDPROC, again by default, will look for, and if found, edit
your FILES.BBS file (used on Opus BBS systems). It will update the
filenames in the FILES.BBS file to reflect the new .PAK file
extensions. If damaged files are deleted, it will remove the entry
from FILES.BBS.
By specifying the /F switch, UDPROC will NOT touch the
FILES.BBS file. It will be left in the same condition it was prior
to UDPROC being executed.
(NOTE: If you are not running an OPUS BBS, and you have no
FILES.BBS file, the /F is basically useless. However, it may help
UDPROC to execute a little faster if you do specify it)
/a or /A Add newly PAK'd archives to FILES.BBS
UDPROC, by default, does not add archive filenames to the
FILES.BBS file if they are not already in it. If you specify the /A
switch however, then UDPROC will add the archive file name to the end
of the FILES.BBS file with a description of (Description Missing).
NOTE: If the /F switch is specified then the /A switch is ignored.
Upload Directory Processor (C) 1990 ZebbWare Products 16/Jan/1990 Page 6
Examples
(Key)
<CR> means hitting the RETURN or ENTER key
(Example #1)
UDPROC /dc:\dos\archives /hc:\archive.hdr /o3 /w <CR>
(Program Logic - A Basic Overview)
Get a Filename in directory \dos\archives on drive c:
IF it has a .ZIP, .LZH, .ICE, .ARC, .PAK extension
if It's .ARC rename it to .PAK & update FILES.BBS
IF it's .ICE rename it to .LZH & update FILES.BBS
If it's .PAK
Test it (PAK T {filename})
if it had errors in it
rename it to {filename}.DAM (/o3 was specified)
copy info from FILES.BBS to DAMAGED.BBS
if it didn't have errors
Convert it (PAK C {filename})
Header was specified so add it
(PAK H {filename} @c:\archive.hdr)
If it's .ZIP
Delete corresponding .PAK file if any (/w was specified)
Un Zip it
if it had errors in it
rename it to {filename}.DAM (/o3 was specified)
copy info from FILES.BBS to DAMAGED.BBS
if it didn't have errors
Convert it (PAK A {filename} {files from .Zip archive})
Header was specified so add it
(PAK H {filename} @c:\archive.hdr)
/o3 was specified so don't delete {filename}.ZIP
If it's .LZH
Delete corresponding .PAK file if any (/w was specified)
Un LHArc it
if it had errors in it
rename it to {filename}.DAM (/o3 was specified)
copy info from FILES.BBS to DAMAGED.BBS
if it didn't have errors
Convert it (PAK A {filename} {files from .LZH archive})
Header was specified so add it
(PAK H {filename} @c:\archive.hdr)
/o3 was specified so don't delete {filename}.LZH
Loop until no more files in directory
Upload Directory Processor (C) 1990 ZebbWare Products 16/Jan/1990 Page 7
Temporary Files & Directorys
UDPROC Creates the following temporary files & directory.
Directory ├┼┼┼┼┼┼┤ is used to unzip & unlzh archives into,
and then it is used by pak to PAK up its contents. Should you get
stuck with this directory, it can be accessed by using the ascii
values: HOLD THE ALT KEY, press 1, 9, 5 on the keypad, RELEASE ALT KEY
HOLD THE ALT KEY, press 1, 9, 7 on the keypad, RELEASE ALT KEY
HOLD THE ALT KEY, press 1, 9, 7 on the keypad, RELEASE ALT KEY
HOLD THE ALT KEY, press 1, 9, 7 on the keypad, RELEASE ALT KEY
HOLD THE ALT KEY, press 1, 9, 7 on the keypad, RELEASE ALT KEY
HOLD THE ALT KEY, press 1, 9, 7 on the keypad, RELEASE ALT KEY
HOLD THE ALT KEY, press 1, 9, 7 on the keypad, RELEASE ALT KEY
HOLD THE ALT KEY, press 1, 8, 0 on the keypad, RELEASE ALT KEY
File YES│NO.TMP - Contains the letter 'Y'. it is used in
deleting the entire contents of the ├┼┼┼┼┼┼┤ directory.
File HDR│RSP.TMP - Contains the extended archive header filename
you specified with the /H switch.
NOTE: That strange character between YES & NO in YES│NO.TMP can
be accessed by:
HOLD THE ALT KEY, press 1,7,9 on the keypad, RELEASE ALT KEY
<Alt>179 is also the character used between HDR & RSP in HDR│RSP.TMP.
Ideally you should never see the above files or directory.
Error & Return Codes
-1 = No directory entered on Command line or when prompted for it
0 = Program successfully completed
10 = Directory does not exist
11 = Header File does not exist
12 = Invalid switch specified on the command line
Required Programs (Setup & Memory Information!)
NoGate Consulting's PAK.EXE, PKWARE's PKUNZIP.EXE, and Yoshi's LHARC.EXE
programs are required to use this utility. They must reside somewhere in
your DOS path environment (ie SET PATH = ). UDPROC performs no actual
archiving. This is done by the 3 above mentioned programs. UDPROC does,
however, call these programs to do the work for you. If you don't know
about Dos PATH's I suggest you read your DOS manual.
Also, since UDPROC calls these programs which in turn read other
programs into memory, you should have AT LEAST 350K available when
executing UDPROC. (In other words, don't run UDPROC on top of OPUS when
you are using some conventional memory for a ramdisk!). MORE is BETTER!
Last Word : "Electrodynamics"